Atlas Knowledge Base
Dashboard
Installing & Uninstalling

Installing & Uninstalling


The SBN Services installer puts the SBN Services and their browser-based Dashboard onto a server, in one folder, in a single guided run. The same script installs a new server, upgrades an existing one, and can put more than one independent set of Services side by side on the same machine. The installer checks for the prerequisites it needs and tells you if anything is missing.

Versioning

SBN Services has its own independent version number — for example 1.3.15 — the same scheme used by SBN Search and SBN Tunnel. It is no longer tied to the SBN release numbering (the v95 / v96 build scheme), so it does not have to match the SBN application release you run elsewhere.

The installed version is shown in the Dashboard header, and the installer reports it as it runs. Upgrading is simply a matter of running the installer from a newer package — your settings, service names, keys and certificates are all preserved.

Installing

The install is the same on every platform: download the package, extract it, and run the install script with administrator rights from the folder you extracted to.

  1. Download sbn-services.<version>.<platform>.<ext> from the SBN Services area of your Innovative Releases portal. The .NET 8 runtime the package needs is covered in .NET 8 Runtime.
  2. Extract it into a working folder on the server. The install script sits at the root of the extracted package.
  3. Run the install script from that folder:
PlatformRun it with
Windows.\install.ps1 from an elevated PowerShell window (Run as Administrator)
Linux and macOSsudo ./install.sh

Answer the questions it asks, review the plan it prints, and confirm. It asks which set of Services to install or upgrade, the port the Dashboard listens on, and where to install. Leave the set name off and you get the default set; give one and you get an independent set with its own services, settings and folders alongside any others on the machine.

Every run writes install.log beside the install script, recording everything it did.

Platform notes

  • Windows — the package is sbn-services.<version>.windows.zip. Each role runs as its own Windows service. Add -QuickInstall to upgrade with no prompts, taking every default.
  • Linux — the package is sbn-services.<version>.linux.tar.gz; extract it with tar -xzf. Program files go to /opt/innovative/sbn-services for the default set and /opt/innovative/<set>-sbn-services for a named one, and logs to /var/log/innovative/sbn-services. Each role runs as the systemd unit sbn-services-<set>-<role>, with the Dashboard at sbn-services-default-dashboard.service; check one with systemctl status sbn-services-default-dashboard. ./install.sh --help lists every option and touches nothing; the ones a normal installation may need are --instance-name <set>, --port <n>, --install-root <path>, --quick (upgrade with no prompts, taking every default), and --dry-run (print what a real run would do, and change nothing).
  • macOS — the services run under launchd rather than systemd, and their files sit under /Library. The macOS package is not yet generally available; contact support if you need one.

Updating

Run the same installer from a newer package. It detects the existing install and offers to upgrade it, showing you the version it found. Adding -QuickInstall (Windows) or --quick (Linux) upgrades with no prompts, taking every default.

Uninstalling

Run the uninstaller with administrator rights from the same folder you installed from:

PlatformRun it with
Windows.\uninstall.ps1 from an elevated PowerShell window
Linux and macOSsudo ./uninstall.sh

That removes the default set. Name a set to remove that one instead, or ask for every set on the server — each one is still confirmed by name. Settings and data left behind are kept unless you ask for them to be purged. The run writes its log beside the uninstaller.

Platform notes

  • Linux — --instance-name <set> removes a named set and --all removes every set on the server. --purge also deletes the settings and data left behind, --force skips the confirmations, and --dry-run shows what would be removed without removing it.
  • macOS — the launchd services are removed in place of the systemd units. The macOS package is not yet generally available; contact support if you need one.


Was this helpful?